Read about different retail use cases for CockroachDB in production today!
Read moreTomorrow, as you undoubtedly know, is day-one of an annual two-day retail event known as “Amazon Prime Day”. Two days of frenetic consumerism that stress Amazon’s architecture in much the same way that Black Friday and Cyber Monday stress the whole retail industry. In 2018 Amazon’s site served a 404 error for hours on Prime Day. But there’s no need to pick on Amazon…J. Crew, Macy’s, H&M, Lowes and others have all endured costly downtime during peak traffic. Three years of masks and stay-at-home mandates forced users to online shopping and forced retailers to scale their online operations to serve unprecedented customer volume. Some even had to establish their first-ever digital presence in order to survive widespread lockdowns that shuttered physical retailers.
Survivability established, next came the need to meet equally unrelenting customer demands for fast and personalized user experiences across a vast spectrum of digital devices and platforms. Now elastic scalability, sophisticated personalization, and a seamless omnichannel experience are simply table stakes for modern retail organizations.
That’s why choosing the right database infrastructure has become a business imperative. Not just to support surging high-transaction workloads, but also to ensure survival in the face of several dire trends facing retailers today.
Beyond meeting the permanently high bar of always-on, personalized, and portable shopping experiences that consumers now expect as a matter of course, modern retail organizations must also contend with a few current trends that are, unfortunately, here to stay:
Responding effectively to these trends requires a modern database infrastructure that can support the variable high transaction workloads of modern retailers and integrate data from an ever-expanding number of applications and services.
Item availability, pricing, and speed of delivery are the prime differentiators customers now seek from a retailer. Satisfying customers by providing all three at the same time, however, means playing a massive game of three-dimensional chess…Where the pieces are continually and unpredictably rearranged by the negative trends we just examined.
Complexity abounds. To keep customers satisfied, retailers need a global view of store-owned ERP systems, discrete inventory management systems, manufacturer fulfillment systems, transportation and logistics that support company processes, and last-mile delivery services. Each, of course, bearing its own set of data.
Retailers aren’t just passively viewing or accessing data from this plethora of applications and systems, unfortunately. Frequently they also must integrate them with third-party solutions, which use the data for even more analysis and other processes or services.
As an example, let’s take a look at last-mile delivery. Many retailers offer a variety of shipping options: standard, priority, two-day, next day. Increasingly, however, many customers want same-day delivery.
Building organizational capacity for same-day service is prohibitive; even Amazon offers same-day delivery in just a few limited markets. However, a slew of same-day delivery services like DoorDash, Shipt, Postmates, and more have popped up to meet this strong consumer demand. Watch: How DoorDash builds future-proof, scale-out systems
A retailer can partner with these services to offer same-day delivery, but this requires tight integration of in-store point of sale systems and inventory with one or more third-party delivery apps. That means careful balancing to ensure that supply not only meets demand, but also gets it to the right customer, on time, across an array of possible delivery windows.
Accurate real-time information is required at every step of the process to ensure that customers get the right information about product availability, and orders are delivered correctly and on time. A database that can deliver this information is crucial.
By now, most companies understand the competitive advantages of basing their operations in the cloud. The flood of retailers undergoing digital transformation prior to 2020 turned into a tsunami once the pandemic hit. According to a March 2021 survey by Flexera, 99% of companies now have a cloud adoption strategy, with 92% opting for a multi-cloud option.
Retailers turn to the cloud to capture unparalleled performance, scalability, and the ability to respond dynamically to ever-evolving customer demands. A, B, and C are all things we get because of distributed architecture. But it’s not just infrastructure that is migrating to the cloud — transactions and data need to come right along with it. Companies who build a custom bridge from the cloud back to their legacy databases are often surprised to find that they don’t experience the performance, scalability, and availability they expected. Pairing next-gen cloud infra with an aging and inflexible legacy database creates inevitable bottlenecks that are both difficult to overcome — and also completely unnecessary.
To capture the full power of the cloud and stay ahead of the competition, forward-thinking retailers are moving to cloud-native digital databases. This is happening because cloud-native databases are the best way to deliver the support for distributed real-time processing/transactions that retailers require.
Case in point: Lush Fresh Handmade Cosmetics operates 950 stores in 49 countries and processes 165,000 financial transactions per day. Accurate, real-time insight into their global inventory, both on hand for point of sale as well as in the pipeline from suppliers, made it critical for their global inventory management database to be ultra-resilient with no outages or downtime. The company selected CockroachDB for its zero RPO (recovery point objective) and an average of 4.5 second RTO (recovery time objective) — ensuring that data is never lost and applications are highly available. Lush also found that having a managed database in the cloud allowed the company’s engineering team to focus on application development instead of maintaining third-party software. (Watch: Why LUSH migrated from Google Spanner to CockroachDB).
Surging high-transaction loads and supply chain challenges are now a fact of life for retailers, and it’s not going to get easier. Marketplace unpredictability has grown as climate change throws ever more frequent curveballs, influencing both customer demand and a retailer’s ability to fulfill it. But: as Sun-Tzu observed more than 2,000 years ago, “With chaos comes opportunity”. Retailers who can roll with the coaster can meet customer needs, while competitors run off the tracks.
Companies everywhere are moving to the cloud. But many of them are still making the mistake of taking their legacy database (and all its technical debt) along with them. Retailers investing in a cloud-native, distributed SQL database like CockroachDB find fewer obstacles, more freedom, greater efficiency, and less fear of Black Friday outages…
…Allowing them to maintain the advantage in the high-stakes game of three dimensional chess that modern retail has become.
Disasters happen. (Most) outages shouldn’t.
When multi-billion dollar companies like Zoom, Slack, and Fanduel experience …
Read moreA request came across my desk the other day asking whether I had any experience with Django and could I get it to work …
Read moreEvery day Lush processes hundreds of thousands of transactions in over 950 stores located across 49 different countries. …
Read more